Toolbar dashboard functionality

ABSTRACT

A system described herein includes a receiver component that receives an indication that a user has selected a first selectable buttontab in a toolbar installed in a client application. The system further includes a display component that causes a dashboard to be displayed on a display device in response to receipt of the indication that the user has selected the buttontab. The dashboard includes a content window that displays content and the buttontab, wherein the dashboard is a seamless visual combination of the buttontab and the content window.

BACKGROUND

Modern personal computers can be equipped with a multitude ofapplications that facilitate performance of a variety of tasks includingbut not limited to word processing tasks, generation of one or morespreadsheets, photo editing, instant messaging, Internet browsing,amongst others. In many of these applications, specialized toolbars canbe installed. Pursuant to an example, a toolbar can be downloaded by wayof the Internet and installed in an Internet browser. Once installed,the toolbar can allow a user to quickly obtain access to one or more websites or services. For instance, the toolbar may be displayed in aframespace of the Internet browser and may include a plurality ofselectable buttons.

Typically, selection of one of the buttons in the toolbar causes a newbrowser window or tab to be opened, wherein the browser window or tab isdirected to a certain site corresponding to the selected toolbar button.In some instances, however, it may be inconvenient for the user to havea new browser window presented over an existing browser window and/or tohave the browser navigate away from a web page that is currently beingperused by the user.

In addition, some toolbars may be configured with one or more selectablebuttons that when selected, direct the user to a web page that requestsuser credentials (e.g., user name and password). Once the user hasprovided such credentials and the credentials have been verified, thetoolbar can be customized in accordance with predefined preferences ofthe user. Thus, type of buttons and arrangement of buttons may bedisplayed in the toolbar in accordance with predefined user preferences.Again, however, requiring the user to navigate to a new page to providesign-in credentials may be inconvenient to the user. Furthermore,requesting user credentials in such a manner may leave the usersusceptible to a phishing attack. For instance, a sophisticated hackermay create a graphical user interface that looks substantially similarto a graphical user interface used by the intended recipient of the usercredentials. Thus, a user may unknowingly provide their credentials tomalicious source.

SUMMARY

The following is a brief summary of subject matter that is described ingreater detail herein. This summary is not intended to be limiting as tothe scope of the claims.

Various technologies pertaining to a toolbar application that can beinstalled in a client-side application such as a word processingapplication, a spreadsheet application, an Internet browser, etc. aredescribed in greater detail herein. In an example, the toolbarapplication can be a graphical user interface application that includesa selectable buttontab. Upon selection of the buttontab (e.g., throughuse of a pointing and clicking mechanism), a dashboard can begraphically displayed to a user on a display screen of a computingdevice. A dashboard can be visually depicted as a visually seamlesscombination with a buttontab and a content window. That is, a buttontaband the content window are graphically depicted in a visually seamlessmanner. Pursuant to an example, at least a portion of the dashboard maybe displayed over a viewing/editing area of the client application(e.g., outside of the framespace of an Internet browser and over aviewing area of the browser).

In an example, the buttontab in a toolbar may be configured to receiveuser credentials from a user. When the user selects the buttontab, adashboard can be graphically displayed to the user, wherein the contentwindow of the dashboard includes one or more fields for receiving usercredentials. As the dashboard is graphically depicted as a seamlesscombination of the buttontab and the content window, a malicious hackerattempting to phish for user credentials would have difficultygenerating a graphical user interface that mimics a graphically depicteddashboard. Specifically, as the dashboard is a seamless combination ofthe buttontab and the content window and extends in the viewing area ofthe client application, a hacker would have difficulty generating agraphical equivalent of such seamless combination as it exists in theframespace of a client application.

Still further, when the buttontab corresponding to receiving usercredentials is selected by a user, a certificate of a site that is toreceive such user credentials can be analyzed. If the certificate isverified, a graphical indicator can be presented in the toolbar toinform a user that they can safely provide their credentials. Forinstance, a color of at least a portion of the toolbar can change (e.g.,to green). In another example, another graphical indicator may bepresented to the user to indicate that a certificate of the sitereceiving the user credentials has been verified (such as a graphicalicon of a lock). Still further, if the site certificate is not verified,the toolbar can present a graphical indication to the user such asturning red.

The example toolbar described herein can also include numerous otherbuttontabs, wherein the buttontabs may operate differently when hoveredover or selected depending on whether or not the user has provided validuser credentials. For instance, if the user has not provided usercredentials, the buttontabs can appear as buttons when hovered over by apointing and clicking mechanism. Furthermore, when selected, thebuttontabs can cause a new browser window or browser tab to be openedand directed towards a web site corresponding to the selected buttontab.In another example, selection of a buttontab may cause a browser to beredirected to a web site corresponding to the buttontab.

If the user has provided user credentials, the buttontab may bepresented as a selectable tab (upside down “U” shaped) when a pointingand clicking mechanism is hovered over the buttontab. If a buttontab isselected, a dashboard corresponding to the buttontab may be displayed,wherein the dashboard is a seamless combination of the selectedbuttontab and a content window. For instance, if the buttontab pertainsto e-mail, the content window of a dashboard can provide a user with asnapshot view of contents of the user's e-mail inbox without requiringthe user to direct the browser to a different web page or open a newbrowser window. Other buttontabs described herein may correspond tocalendar data, photographs, news items, sharing data, a profile of theuser, and/or other social networking data.

Other aspects will be appreciated upon reading and understanding theattached figures and description.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a functional block diagram of an example system thatfacilitates displaying a dashboard in a client application through useof a toolbar.

FIG. 2 is a functional block diagram of an example system thatfacilitates receiving user credentials by way of a dashboard in atoolbar.

FIG. 3 is a functional block diagram of an example system thatfacilitates displaying a buttontab in a particular manner upon apointing and clicking device hovering over the buttontab.

FIG. 4 is a functional block diagram of an example system thatfacilitates display of a buttontab in a particular manner upon apointing and clicking mechanism being hovered over the buttontab.

FIGS. 5-12 are example graphical user interfaces that depict a dashboarddisplayed in connection with a toolbar in a client application.

FIG. 13 is flow diagram that illustrates an example methodology fordisplaying a dashboard from a toolbar in a client side application.

FIG. 14 is a flow diagram that illustrates an example methodology fordisplaying a dashboard in a certain manner depending on a buttontabselected by a user.

FIG. 15 is an example computing system.

DETAILED DESCRIPTION

Various technologies pertaining to dashboards that can be displayed fromtoolbars installed in a client application will now be described withreference to the drawings, where like reference numerals represent likeelements throughout. In addition, several functional block diagrams ofexample systems are illustrated and described herein for purposes ofexplanation; however, it is to be understood that functionality that isdescribed as being carried out by certain system components may beperformed by multiple components. Similarly, for instance, a componentmay be configured to perform functionality that is described as beingcarried out by multiple components.

With reference to FIG. 1, an example system 100 that facilitatesdisplaying a dashboard from a toolbar installed in a client applicationis illustrated. The system 100 includes a display device 102 that mayexist on a client computer such as a personal computer, a personaldigital assistant, a mobile telephone, a laptop computer, etc. Thus, thedisplay device 102 may be or include a liquid crystal display screen, acathode ray tube display screen or other suitable display screen. Thedisplay device 102 may display a graphical user interface pertaining toa client application 104 to a user. The client application 104 may be,for instance, an Internet browser, a word processing application, aspreadsheet application, a slideshow application, or any other suitableapplication that can be executed on the client computing device.

The client application 104 may include a toolbar 106, which may be anadd-on or plug-in application to the client application 104. Forexample, the toolbar 106 may be a search toolbar that is downloaded tothe client computing device by way of the Internet and installed in theclient application 104, which may be an Internet browser.

The toolbar 106 can include a plurality of selectable buttontabs108-110. As will be described in greater detail below, functionality ofthe plurality of buttontabs 108-110 may depend on whether or not theuser has provided valid user credentials (e.g., user name and password)to the toolbar 106. Pursuant to an example, upon selection of thebuttontab 108 a dashboard 112 can be visually presented to the user onthe display device 102. As used herein, a dashboard can be a visuallyseamless combination of a buttontab and a content window 114, whereinthe content window 114 displays information pertaining to the buttontabselected by the user. For instance the buttontab 108 may pertain toe-mail, and the content window 114 can display at least a portion of ane-mail inbox of the user upon the buttontab 108 being selected.

The system 100 may also include a receiver component 116 that receivesan indication that the user has selected the first buttontab 108 in thetoolbar 106 installed in the client application 104. For instance, theuser may select the first buttontab 108 through use of a pointing andclicking mechanism such as a mouse. The system 100 may also include adisplay component 118 that causes the dashboard 112 to be displayed onthe display device 102 in response to receipt of the indication that theuser has selected the first buttontab 108. As noted above, the dashboard112 is a visually seamless combination of the buttontab 108 and thecontent window 114.

As will be shown and described in greater detail below, the toolbar 106can include a plurality of different types of buttontabs. For instance,the toolbar 106 may include a buttontab pertaining to receipt of usercredentials, pertaining to user e-mail, pertaining to photographs (e.g.,taken by the user and/or posted by contacts in the user's socialnetwork), a buttontab pertaining to calendar data, a buttontabpertaining to uploading data to a web site that can be viewed bycontacts in the user's social network, a buttontab pertaining to aprofile of the user, a buttontab pertaining to news, amongst otherbuttontabs. Thus, the display component 118 can be configured to displaydashboards pertaining to each of the buttontabs upon receiving anindication that the user has selected one of such buttontabs.Furthermore, the display component 118 can graphically modify thetoolbar 106 when content of a dashboard has changed, when a reminder isto be issued to a user, when certificates of a site that receives usercredentials has been authorized, etc.

Referring now to FIG. 2, an example system 200 that facilitatesinforming a user that a site that is to receive user credentials isassociated with valid certificates is illustrated. The system 200includes the display device 102, the client application 104, and thetoolbar 106. Additionally, the toolbar 106 includes the selectablebuttontabs 108-110. Furthermore, the system 200 includes the receivercomponent 116 and the display component 118 which can act in conjunctionas described above.

In this example, the user has selected the first buttontab 108 whichpertains to allowing a user to sign in to the toolbar 106. Upon receiptof an indication that the user has selected the first buttontab 108, thedisplay component 118 can cause the dashboard 112 to be displayed in theclient application 104 on the display device 102. The content window 114can include at least entry field for receiving user credentials 202. Forinstance, the entry field(s) for receiving user credentials 202 can beconfigured to receive a user name and/or password.

The system 200 may further include a security component 204, wherein thesecurity component 204 can access one or more certificates of a site 206(web site) that is to receive user credentials entered by way of theentry field(s) for user credentials 202. Pursuant to an example, thesecurity component 204 can access these certificates upon the receivercomponent 116 receiving an indication that the user has selected thebuttontab 108. If the security component 204 finds that certificates ofthe site 206 are valid, the security component 204 can output anindication that such certificates are valid. The display component 118can receive the indication from the security component 204 that thecertificates are valid, and can cause a graphical indicia 208 to bedisplayed on the toolbar 106 to indicate to the user that the one ormore certificates pertaining to the site 206 are valid.

For instance, the display component 118 can cause at least a portion ofthe toolbar 106 to change color. In a specific example, the displaycomponent 118 can cause the toolbar 106 to turn green if the securitycomponent 204 indicates that the certificates pertaining to the site 206are valid. In another example, the display component 118 can cause agraphical icon to appear on the toolbar 106, such as a graphical icon ofa lock to indicate that the certificates pertaining to the site 206 havebeen found to be valid and that the user can enter their usercredentials into the entry field(s) for user credentials 202 withconfidence. In yet another example, the display component 118 can causeanimation to appear in the toolbar 106 to indicate to the user that theuser can enter their user credentials into the entry field(s) for usercredentials 202 with confidence. In still yet another example, thesystem 200 may include an audio component 210 that is in communicationwith the security component 204. For instance, security component 204can indicate that certificates pertaining to the site 206 are valid (orinvalid), and the audio component 210 can output an audible indicia tothe user to indicate that certificates pertaining to the site 206 arevalid (or invalid).

Furthermore, the security component 204 may access one or morecertificates pertaining to the site 206 and determine that suchcertificates are not valid (e.g., the site 206 may be used in connectionwith a man in the middle attack to maliciously receive user credentialsfrom the user). The security component 204 may output an indication thatcertificates pertaining to the site 206 are not valid, and suchindication can be received by a display component 118. Responsive toreceiving such an indication, the display component 118 can modify thetoolbar 106 to indicate to the user that the user should not provideuser credentials into the entry field(s) for user credentials 202. Forinstance, the display component 118 can cause at least a portion of thetoolbar 106 to change color. In a specific example, the displaycomponent 118 can cause at least a portion of the toolbar 106 to changeto the color red. Similarly, the display component 118 can cause agraphical icon to be displayed, animation to be displayed, or an audibleoutput to be generated to indicate to the user that the user should notprovide user credentials into the entry field(s) for user credentials202.

Furthermore, as noted above, the display component 118 can graphicallydisplay the dashboard 112 as being a visually seamless combination ofthe buttontab 108 and the content window 114 (which includes the entryfield(s) for user credentials 202). Due to such seamless combination, amalicious hacker may find it difficult to generate a phishing attackagainst the user to illicitly receive user credentials. Particularly,the display component 118 can cause the dashboard 112 to be displayed inthe framespace of the client application 104 and also simultaneously bedisplayed in a viewing area/editing area of the client application 104.Thus, the dashboard 112 can appear to extend from the framespace of theclient application 104 and over a viewing/editing area of the clientapplication. As phishing attacks are typically limited to theviewing/editing area of client applications, a malicious hacker wouldfind it difficult to mimic the visual presentation of the dashboard 112(the visually seamless combination of the selectable buttontab 108 andthe content window 114).

Referring now to FIG. 3, an example system 300 that facilitatesdisplaying a buttontab in a toolbar in a particular manner depending onwhether or not a user has provided valid user credentials isillustrated. The system 300 includes a display device 102 that displaysthe client application 104 to the user. The toolbar 106 is installed anddisplayed in the framespace of the client application 104. The toolbar106 includes the buttontabs 108-110. Furthermore, the client application106 can include a viewing/editing window 302, which can display editableand/or noneditable content to the user. For instance, if the clientapplication 104 is an Internet browser, the viewing/editing window 302can display content of a web page to the user. In another example, ifthe client application 104 is a word processing application, theviewing/editing window 302 may include content generated by the user andindicia indicating that the user can edit information shown in theviewing/editing window 302.

The system 300 additionally includes a hover component 304, wherein thehover component 304 is configured to detect that a pointing mechanism306 such as a mouse is being hovered over the buttontab 108. The displaycomponent 118, upon receiving an indication from the hover component 304that the pointing mechanism 306 is being hovered over the buttontab 108,can select one of at least two manners of which to display the buttontab108 depending upon whether or not the user has provided valid usercredentials to the toolbar 106. In this example, upon the hovercomponent 304 detecting that a pointing mechanism 306 is being hoveredover the buttontab 108, the display component 118 can cause thebuttontab 108 to appear as a selectable button within the framespace ofthe toolbar 106. For instance, edges of the buttontab 108 can bedisplayed to the user and/or made to appear darker, in a differentcolor, etc., such that the user can clearly determine that the pointingand clicking mechanism is being hovered over the buttontab 108 and, ifthe left mouse button is clicked, the buttontab 108 will be selected(and the buttontab 110 will not be selected).

Referring now to FIG. 4, an example system 400 that facilitatesdisplaying a buttontab in a toolbar in a particular manner depending onwhether or not a user has provided valid user credentials to the toolbaris illustrated. The system 400 includes the display device 102 thatdisplays a client application 104 that includes a toolbar 106, whereinthe toolbar 106 is located in the framespace of the client application104. The toolbar 106 includes the plurality of buttontabs 108-110.Additionally, the client application 104 includes the editing/viewingwindow 302.

In this example, the user may have provided valid user credentials tothe toolbar 106. The hover component 304 can detect that the pointingmechanism is hovering over the buttontab 108 and can output anindication of such a detection. The display component 118 can receive anindication from the hover component 304 and can cause the buttontab 108to be displayed as a tab in the toolbar 106. For instance, the buttontab108 can be displayed in the general shape of an upside down “U: suchthat sides of the buttontab 108 can intersect with a bottom edge of thetoolbar 106. In this example, the bottom edge of the toolbar 106 isshown as being adjacent to the top edge of the viewing/editing window302 of the client application 104. It is to be understood, however, thatthe bottom edge of the toolbar 106 may be adjacent to a top edge ofanother toolbar, for instance. Pursuant to an example, when the userselects the buttontab 108, a dashboard can be displayed to the user thatincludes content pertaining to the buttontab 108.

Referring now to FIG. 5, an example graphical user interface 500 of atoolbar found in a client application is illustrated. The graphical userinterface 500 includes a graphical user interface for a clientapplication 502. In this example, the client application may be anInternet browser. The graphical user interface 500 additionally includesa depiction of a toolbar 504, wherein the toolbar 504 can be a toolbarthat may be used in connection with executing a search. Accordingly, thetoolbar 504 can include a search field 506 which is configured toreceive search queries from a user. The toolbar 504 can additionallyinclude a search button 508 that, when depressed, causes a search to beundertaken based upon a query provided by the user in the search field506. The toolbar 504 additionally includes a plurality of buttontabs510-512. For instance, the buttontabs 510-512 can be depicted as textwith no discriminating lines therebetween unless a pointing and clickingmechanism 514 is hovered over the appropriate buttontab. In anotherexample, the buttontabs 510-512 may be depicted as graphical icons,animation and/or the like.

As depicted, one of the buttontabs 510-512 can be a buttontab configuredto receive user credentials when selected by a user by way of thepointing mechanism 514. For instance, the buttontab 512 may be assigneda name that indicates to a user that, upon selection of the buttontab512, the user will be provided with a utility for entering the usercredentials.

Upon selection of the buttontab 512 through use of the pointingmechanism 514, a dashboard 516 can be presented to the user, wherein thedashboard 516 is a seamless visual combination of the buttontab 512 anda content window 518. Thus as shown in FIG. 5, a dashboard 516 isvisually depicted as overlaying at least a portion of the toolbar 504 aswell as at least a portion of a viewing area 520 of the clientapplication 502. The content window 518 can include a user credentialfield 522 that is configured to receive credentials of a user, such as auser name and password. The content window 518 may also include aselectable button (not shown) that causes the user credentials providedby the user to be transmitted to a server for validation. Furthermore,while not shown, when the buttontab is selected by the user, at least aportion of the toolbar 504 can be subjected to a color change forinstance. Similarly, a graphical icon can be presented to the user toindicate that the user can provide user credentials with confidence.

With reference now to FIG. 6, an example graphical user interface 600 isillustrated. The graphical user interface 600 depicts a clientapplication 602. The client application 602 includes a toolbar 604installed as an add-on/plug-in to the client application 602. Thetoolbar 604 can be located in the framespace of the client application602, which is visually separated from a viewing area 606 of the clientapplication 602. The toolbar 604 includes the search field 506 and thesearch button 508 which act as described above. The toolbar 604 alsoincludes a plurality of selectable buttontabs 610-614. As shown, thebuttontab 614 displays an identity of the user that has provided validcredentials to the toolbar 604. Thus, such buttontab 614 can correspondwith or include an avatar that has been selected by the user.

Furthermore, the exemplary buttontab 610 pertains to e-mail of the userthat has provided valid credentials to the toolbar 604. Upon selectionof the buttontab 610, a dashboard 616 can be presented to the user,wherein the dashboard is a visually seamless combination of thebuttontab 610 and a content window 618. Furthermore, the dashboard 616can be shown as covering at least a portion of a toolbar 604 as well asat least a portion of the viewing area 606 of the client application602. The content window 618 of the dashboard 616 may display at least aportion of an e-mail inbox of the user. For instance, the content window618 can shown a threshold number of most recently received e-mailmessages in the inbox of the user. Additionally, the content window 618can depict to the user which of the e-mail messages shown in the contentwindow 618 are unread, marked as urgent, etc. (e.g., by causing certainemails to be displayed boldly, in a certain font, displaying graphics, .. . ). Still further, the content window 618 may display, senders ofe-mail messages, times that the e-mail messages were received, subjectlines of e-mail messages, portions of e-mail messages, etc. Stillfurther, the dashboard 616 can facilitate interactivity with the e-mailinbox of the user. For instance, the user may select a message in thedashboard 616 and reply to a message directly within the dashboard 616.In another example, upon selection of a message in the dashboard 616, anew browser window or browser tab can be opened that directs the user toan e-mail inbox of such user, to the selected message, etc.

Moreover, the dashboard 616 is shown as being a particular shape -however, such dashboard 616 may be any suitable shape, so long as thedashboard 616 is a visually seamless combination of the buttontab 610and the content window 618. For instance, the content window 618 isshown as being generally square in nature, extending vertically from afirst side of the buttontab 610 and extending horizontally past a secondside of the buttontab 610. The content window 618, however, may beshaped as any suitable shape, and can be positioned with respect to thebuttontab 610 in any suitable manner. For instance, the content window618 may be ovular in nature. In another example, the content window 618can be placed such that it extends horizontally from the left side ofthe buttontab 610 (instead of the right side of the buttontab 610 asshown in FIG. 6). Further, the content window 618 may extendhorizontally in both directions from both sides of the buttontab 610. Amanner in which the dashboard 616 is displayed can be based upon size ofa browser window, an amount of content to be shown in the content window618, position of the buttontab 610 in the toolbar 604, etc.

Turning now to FIG. 7, an example graphical user interface 700 isdepicted. The graphical user interface 700 includes a depiction of theclient application 602, the toolbar 604, the search field 506 and searchbutton 508, and the selectable buttontabs 610-614. In this example, theselectable buttontab 610 pertains to calendar data of a user who hasprovided valid credentials to the toolbar 604. Thus, upon the userselecting the buttontab 610 through use of the pointing mechanism 514,calendar data pertaining to the user can be presented. Specifically,upon selection of the buttontab 610 a dashboard 702 can be graphicallypresented to the user, wherein the dashboard 702 is a seamless visualcombination of the buttontab 610 and a content window 704. The dashboard702 may cover at least a portion of the toolbar 604 and at least aportion of the viewing area 606 of the client application 602.

The content window 704 may include various types of calendar data. Forinstance, the calendar data may be a visual depiction of a month withcertain dates or times highlighted, wherein the user has a calendarevent occurring on such date and/or at such time. Furthermore, thecontent window 704 may include details pertaining to events that arecalendared in a month being viewed by the user and/or within a thresholdamount of time from a current time.

As before, the dashboard 702 may facilitate interactivity between theuser and calendar data of such user. For instance, the user may add ordelete a calendared event directly in the dashboard 702. In anotherexample, upon selection of a date, time, event, etc. a new browserwindow and/or browser tab can be opened, wherein the browser windowand/or browser tab can include calendar data of the user and can allowthe user to edit calendar data.

With reference now to FIG. 8, an example graphical user interface 800 isillustrated. The graphical user interface 800 includes a depiction ofthe client application 602 with the toolbar 604 installed therein as anadd-on or plug-in. In this example, the buttontab 610 may pertain tophotos of a user who has provided valid sign-in credentials and/orphotos of contacts in a social network of the user. Upon selection ofthe buttontab 610 through use of the pointing mechanism 514, a dashboard802 can be visually presented to the user, wherein the dashboard 802 isa visually seamless combination of the buttontab 610 and a contentwindow 804. As described above, the dashboard 802 can cover at least aportion of the toolbar 604 as well as at least a portion of the viewingarea 606 of the client application 602.

The content window 804 can include a plurality of photos, wherein theplurality of photos may be photos recently added to an online photoalbum of the user and/or photos added by social contacts of the user totheir respective online photo albums. Thus, upon selection of thebuttontab 610, the user can be presented with new photos taken bycontacts of the user. Upon selection of one or more of the photosdisplayed in the content window 804, a new browser window or browser tabmay be opened directing the user to an online photo album pertaining toa contact of a user that posted such photo. In another example,selection of one or more of the photos may cause a photo editingapplication to be initiated. Still further, selection of one or more ofthe photos may cause a photo to be enlarged within the content window804. In still yet another example, the user may provide tags to one ormore photos in the content window 804 through use of the dashboard 802.For instance, the dashboard 802 may allow for user interactivity suchthat the user can select one of the photos and add a tag to one or moreof the photos without opening another browser window or browser tab.

Now turning to FIG. 9, an example graphical user interface 900 isdepicted. The graphical user interface 900 may include a depiction ofthe client application 602 and the toolbar 604 as described above. Inthis example, the selectable buttontab 610 may pertain to news items.Accordingly, upon the user that is signed in to the toolbar selectingthe buttontab 610 by way of the pointing mechanism 514, a dashboard 902can be presented to the user wherein the dashboard 902 is a visuallyseamless combination of the selectable buttontab 610 and a contentwindow 904.

The content window 904 can display one or more current news items. Forinstance, the news items may pertain to a known location of a user suchthat the user is provided with customized news. In another example, newsitems presented to the user in the content window 904 may be from a userselected national news source. In still yet another example, the newsitems presented to the user in the content window 904 may be receivedfrom a news organization that corresponds to the toolbar 604 or knowninterests of the user. Upon selection of one or more of the news itemsdepicted in the content window 904, a new browser window or browser tabcan be opened, and the selected story can be presented to the user inthe new browser window or tab. In another example, a selected news itemmay be shown in more detail directly in the content window 904 of thedashboard 902. Thus, the user may have an ability to read a news storywithout being required to open a new browser window or browser tab. Thenews items depicted in the content window 904 may be displayed in anysuitable manner. For instance, news items may be ranked by perceivedrelevance to user interests. In another example, the news itemspresented may be headlines, headlines together with a news summary,abstracts, etc.

Referring now to FIG. 10, an example graphical user interface 1000 isillustrated. In this example, the selectable buttontab 610 pertains tocausing data to be shared with contacts of the user (e.g., contactswithin the social network of the user). Upon selection of the buttontab610 through use of the pointing mechanism 514, a dashboard 1002 can bevisually presented to the user, wherein the dashboard 1002 is a visuallyseamless combination of the selectable buttontab 610 and a contentwindow 1004. Thus, visually it can appear to the user that the buttontab610 expands to show data pertaining to the buttontab. In this example,the content window 1004 may include a data entry field 1006. Pursuant toan example, the data entry field 1006 may be automatically populatedwith a URL of a web site that is currently being viewed through use ofthe client application 602. Thereafter, the user may cause such URL tobe uploaded to a server such that members of the user's social networkcan quickly ascertain which site the user would like to share withhis/her social contacts. In other examples, the user may provide otherdata in the data entry field. For instance, the user may select a fileon the client computing device to upload to the server to a site that isaccessible by one or more contacts of the user. Further, the user mayprovide a description of comments pertaining to data placed in the dataentry field (e.g., comments pertaining to a certain file, a URL, . . .).

Referring now to FIG. 11, an example graphical user interface 1100 isillustrated. As before, the graphical user interface 1100 includes adepiction of the client application 602 and the toolbar 604 installedtherein. In the example depicted in FIG. 11, the selectable buttontab610 pertains to a social network of the user. More particularly, thebuttontab 610 can be used in connection with providing the user withupdates of contacts of the user. Upon selection of the buttontab 610through use of the pointing mechanism 514, a dashboard 1102 can bepresented to the user, wherein the dashboard 1102 is a visually seamlesscombination of the buttontab 610 and a content window 1104. As before,the dashboard 1102 can cover at least a portion of the toolbar 604 aswell as at least a portion of the viewing area 606 of the clientapplication 602.

The content window 1104 can display updates of one or more socialcontacts of the user. For instance, a social contact of the user maychange their status (e.g., from online to offline). In another example,a social contact of the user may change an avatar corresponding thereto,may alter a current mood, may add one or more files to their socialnetworking home page, may modify their user profile, etc. Thus, the userwho has provided valid credentials to the toolbar 604 can quickly viewupdates pertaining to the social network of the user. Upon selection ofone or more updates displayed in the content window 1104, a new browserwindow or browser tab can be opened that directs the user to the socialnetworking page of the contact that corresponds to the update. Inanother example, upon selection of the contact update in the contentwindow 1104, an instant messaging application may be initiated and aninstant messaging conversation window between the user and the contactmay be presented to the user. Other functionality upon selecting acontact update in the content window 1104 is contemplated by theinventors and is intended to fall under the scope of the hereto-appendedclaims.

Referring now to FIG. 12, an example graphical user interface 1200 isshown. The graphical user interface 1200 depicts the client application602 with the toolbar 604 installed therein. In this example, theselectable buttontab 610 may pertain to a profile of a user (e.g., asocial networking profile) who has provided valid sign-in credentials tothe toolbar 604. Upon selection of the buttontab 610 through use of thepointing mechanism 514, a dashboard 1202 can be presented to the user,wherein the dashboard 1202 is a visually seamless combination of theselectable buttontab 610 and a content window 1204. The content window1204 may include editable profile data of the user. For instance, sucheditable data may include a blog entry, an avatar, a current status ofthe user, etc. Thus, the user may alter their social networking statuswithout having to open a new browser window/tab that is directed to asocial networking home page of the user.

While the dashboards shown in FIGS. 5-12 are shown at certain positionsin the toolbar 604, it is to be understood that each of the buttontabsdescribed herein may be simultaneously depicted in the toolbar 604 atany suitable location or order. Furthermore, buttontabs pertaining toother data may also be displayed at any suitable location and in anysuitable order in the toolbar 604. For instance, another buttontab maypertain to a user's instant messaging contacts, wherein selection of thebuttontab may cause each online contact (e.g., each contact logged intoan instant messaging application) of the user to be displayed.Thereafter, an instant messaging conversation can be initiated withinthe dashboard presented upon selection of the buttontab.

Moreover, a maintainer of the toolbar 604 can remotely add buttons tothe toolbar 604, such that certain markets/regions have particularbuttontabs displayed thereon. In another example, a maintainer of thetoolbar 604 can remotely change order of buttontabs for a particularmarket/region. Such changing of buttontabs and/or changing of an orderof display of buttontabs can be undertaken, for instance, by way of anRSS feed. Other mechanisms are also contemplated, however.

With reference now to FIGS. 13-14, various example methodologies areillustrated and described. While the methodologies are described asbeing a series of acts that are performed in a sequence, it is to beunderstood that the methodologies are not limited by the order of thesequence. For instance, some acts may occur in a different order thanwhat is described herein. In addition, an act may occur concurrentlywith another act. Furthermore, in some instances, not all acts may berequired to implement a methodology described herein.

Moreover, the acts described herein may be computer-executableinstructions that can be implemented by one or more processors and/orstored on a computer-readable medium or media. The computer-executableinstructions may include a routine, a sub-routine, programs, a thread ofexecution, and/or the like. Still further, results of acts of themethodologies may be stored in a computer-readable medium, displayed ona display device, and/or the like.

Referring now to FIG. 13, a methodology 1300 that facilitates displayinga dashboard on a display device is illustrated. The methodology 1300begins at 1302, and at 1304 a plurality of selectable buttontabs in atoolbar installed in a client side application are displayed on adisplay screen of a client computing device. As noted above, the toolbarmay be placed in a framespace of the client side application, whereinthe client side application may be an Internet browser, a wordprocessing application, etc.

At 1306, it is determined that a user has selected one of the selectablebuttontabs displayed in the toolbar in the client side application. Asnoted above, the selectable buttontabs may pertain to e-mail of theuser, calendar data of the user, social network of the user, photographsof the user, or of contacts of the user, etc.

At 1308, a dashboard is displayed that comprises information pertainingto the selectable buttontab, wherein the dashboard is displayed upondetermining that the user has selected the selectable buttontab. Asdiscussed previously, the dashboard can be a visually seamlesscombination of the selected buttontab and a content window. Furthermore,the dashboard can be graphically depicted as overlaying at least aportion of the toolbar as well as at least a portion of aviewing/editing window of the client application. The methodology 1300completes at 1310.

Referring now to FIG. 14, a methodology 1400 that facilitates displayinga dashboard in a toolbar installed in a client application isillustrated. The methodology 1400 starts at 1402, and at 1404 aplurality of selectable buttontabs in a toolbar installed in an Internetbrowser are displayed. For instance, the toolbar can be downloaded byway of the Internet and added to the Internet browser as an add-on orplug-in. Furthermore, the plurality of selectable buttontabs can includea first buttontab that pertains to e-mail of a user, a second buttontabthat pertains to a calendar of the user, a third buttontab that pertainsto a social network of the user, a fourth buttontab that pertains to aprofile of the user, a fifth buttontab that pertains to news items, anda sixth buttontab that pertains to uploading data to a server.

At 1406, it is determined that the user has selected one of theselectable buttontabs. At 1408 a dashboard is displayed depending uponwhich of the selectable buttontabs was selected by the user. Thedashboard can be visually depicted as a seamless visual combination ofthe selected buttontab and a content window wherein the dashboard is atleast partially displayed over at least a portion of the toolbar and atleast a portion of a viewing area of the Internet browser.

If the first selectable buttontab is selected, the displayed dashboardcan include at least a portion of an e-mail inbox of the user. If thesecond selectable buttontab is selected, the displayed dashboard caninclude calendar data of the user. If the third selectable buttontab isselected, the displayed dashboard can include data pertaining to socialcontacts of the user. If the fourth selectable buttontab is selected,the displayed dashboard can include profile data of the user. If thefifth selectable buttontab is selected, the displayed dashboard caninclude at least one news item, and if the sixth selectable buttontab isselected, the displayed dashboard can include a data entry field foruploading data to the server. The methodology 1400 completes at 1410.

Now referring to FIG. 15, a high-level illustration of an examplecomputing device 1500 that can be used in accordance with the systemsand methodologies disclosed herein is illustrated. For instance, thecomputing device 1500 may be used in a system that supports displayingdashboards to a user. In another example, at least a portion of thecomputing device 1500 may be used in a system that supports downloadingand installing a toolbar into a client application. The computing device1500 includes at least one processor 1502 that executes instructionsthat are stored in a memory 1504. The instructions may be, for instance,instructions for implementing functionality described as being carriedout by one or more components discussed above or instructions forimplementing one or more of the methods described above. The processor1502 may access the memory 1504 by way of a system bus 1506. In additionto storing executable instructions, the memory 1504 may also storee-mail data of the user, calendar data of the user, social contactinformation of the user, etc.

The computing device 1500 additionally includes a data store 1508 thatis accessible by the processor 1502 by way of the system bus 1506. Thedata store 1508 may include executable instructions, e-mail data of theuser, social contact information of the user, photographs, etc. Thecomputing device 1500 also includes an input interface 1510 that allowsexternal devices to communicate with the computing device 1500. Forinstance, the input interface 1510 may be used to receive instructionsfrom an external computing device, from a user through use of adashboard, etc. The computing device 1500 also includes an outputinterface 1512 that interfaces the computing device 1500 with one ormore external devices. For example, the computing device 1500 maydisplay text, images, etc. by way of the output interface 1512.

Additionally, while illustrated as a single system, it is to beunderstood that the computing device 1500 may be a distributed system.Thus, for instance, several devices may be in communication by way of anetwork connection and may collectively perform tasks described as beingperformed by the computing device 1500.

As used herein, the terms “component” and “system” are intended toencompass hardware, software, or a combination of hardware and software.Thus, for example, a system or component may be a process, a processexecuting on a processor, or a processor. Additionally, a component orsystem may be localized on a single device or distributed across severaldevices.

It is noted that several examples have been provided for purposes ofexplanation. These examples are not to be construed as limiting thehereto-appended claims. Additionally, it may be recognized that theexamples provided herein may be permutated while still falling under thescope of the claims.

1. A system comprising the following computer-executable components: areceiver component that receives an indication that a user has selecteda first selectable buttontab in a toolbar installed in a clientapplication; and a display component that causes a dashboard to bedisplayed on a display device in response to receipt of the indicationthat the user has selected the buttontab, wherein the dashboardcomprises a content window that displays content and the buttontab,wherein the dashboard is a seamless visual combination of the buttontaband the content window.
 2. The system of claim 1, wherein the displayeddashboard is configured to receive user credentials.
 3. The system ofclaim 2, further comprising a security component that accesses one ormore certificates of a site that is to receive the user credentials andoutputs an indication that the one or more certificates are valid,wherein the display component causes a graphical indicia to be displayedon the toolbar to indicate that the one or more certificates are valid.4. The system of claim 3, wherein the graphical indicia is a change ofcolor of at least a portion of the toolbar.
 5. The system of claim 3,wherein the graphical indicia is an icon.
 6. The system of claim 1,wherein the toolbar comprises a second selectable buttontab, and furthercomprising a hover component that detects that a pointing mechanism isbeing hovered over the second selectable buttontab, wherein the displaycomponent selects one of at least two manners of which to display thesecond selectable buttontab depending upon whether the user has provideduser credentials to the toolbar.
 7. The system of claim 6, wherein ifthe user has provided user credentials to the toolbar, the displaycomponent causes the second buttontab to be visually displayed as aselectable tab in the toolbar upon the hover component detecting thatthe pointing mechanism is being hovered over the second selectablebuttontab.
 8. The system of claim 6, wherein if the user has failed toprovide user credentials to the toolbar, the display component causesthe second buttontab to be displayed as a selectable button in thetoolbar upon the hover component detecting that the pointing mechanismis being hovered over the second buttontab.
 9. The system of claim 1,wherein the display component causes at least one of an email message,calendar data, an image, or a news item to be displayed in the contentwindow of the dashboard.
 10. The system of claim 1, wherein the toolbarincludes a plurality of selectable buttontabs, wherein at least one ofthe selectable buttontabs provides access to email, and wherein thedisplay component causes visual display of the at least one of theselectable buttontabs to be altered when a new email is received. 11.The system of claim 1, wherein the toolbar comprises a second selectablebuttontab, and wherein the display component causes a new browser windowto be opened when the user selects the second selectable buttontab. 12.The system of claim 11, wherein the display component only causes a newbrowser window to be opened when the user selects the second buttontabif the user has failed to provide user credentials to the toolbar. 13.The system of claim 1, wherein the client application is an Internetbrowser.
 14. The system of claim 1, wherein the toolbar is graphicallydepicted as being in the framespace of the client application, whereinthe client application includes a viewing/editing area, and wherein thedashboard is visually depicted as extending from the framespace of theclient application and over the viewing/editing area of the clientapplication.
 15. A method comprising the following computer-executableacts: displaying, on a display screen, a plurality of selectablebuttontabs in a toolbar installed in a client application; determiningthat a user has selected one of the buttontabs; and displaying adashboard that comprises the selected buttontab and a content window,wherein the dashboard is a seamless visual combination of the buttontaband the content window, wherein the content window comprises informationpertaining to the selected buttontab, and wherein at least a portion ofthe dashboard is displayed over a viewing window of the clientapplication.
 16. The method of claim 15, wherein the selected buttontabpertains to receipt of user credentials, wherein a visual indication ispresented to the user that a site receiving the user credentials has avalid certificate.
 17. The method of claim 15, wherein the selectedbuttontab pertains to email, and wherein the displayed dashboardincludes at least a portion of an email inbox.
 18. The method of claim15, wherein the selected buttontab pertains to a calendar of the user,and wherein the displayed dashboard includes an upcoming calendar eventof the user.
 19. The method of claim 15, wherein the toolbar isinstalled as one of an add-on or plug-in in an Internet browser.
 20. Acomputer-readable medium comprising instructions that, when executed bya processor, perform the following acts: display a plurality ofselectable buttontabs in a toolbar that is installed in an Internetbrowser, wherein the plurality of selectable buttontabs includes a firstbuttontab that pertains to email of a user, a second buttontab thatpertains to a calendar of the user, a third buttontab that pertains to asocial network of the user, a fourth buttontab that pertains to aprofile of the user, a fifth buttontab that pertains to news items, anda sixth buttontab that pertains to uploading data to a server;determining that the user has selected one of the buttontabs; displayinga dashboard that corresponds to the selected buttontab seamlessly fromthe buttontab, wherein the dashboard is at least partially displayedover a viewing area of the Internet browser, wherein if the firstbuttontab is selected the displayed dashboard includes at least aportion of an email inbox of the user, wherein if the second buttontabis selected the displayed dashboard includes calendar data of the user,wherein if the third buttontab is selected the dashboard includes datapertaining to social contacts of the user; wherein if the fourthbuttontab is selected the displayed dashboard includes profile data ofthe user, wherein if the fifth buttontab is selected the dashboardincludes at least one news item, and wherein if the sixth buttontab isselected the dashboard includes a data entry field for uploading data tothe server.